Process flow definition creating system, process flow definition creating device, and a method of creating process flow definition

ABSTRACT

A process flow definition creating system provides a process flow definition to a system for executing processes in an order in accordance with the process flow definition. The process flow definition creating system includes a device list storage unit; a screen information storage unit, wherein the screen information is for displaying a first field and a second field; a display control unit that displays the parsed screen information; a setting reception unit that receives a setting for the first field and a setting for the second field, wherein the setting for the first field defines the processes and the order of the processes, and the setting for the second field defines correspondence between the processes and devices that are to execute the processes; and a definition creating unit that creates the process flow definition, based on the settings.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a process flow definition creatingsystem, a process flow definition creating device, and a method ofcreating a process flow definition. The process flow definition definesprocesses executed by corresponding devices, and an order of executingthe processes.

2. Description of the Related Art

An information processing system has been known that executes a sequenceof processes. In such an information processing system, an administratoror the like may define a sequence of processes as a workflow in advance.The sequence of processes may include a combination of a typical datainput process, a typical data conversion process, and/or a typical dataoutput process. When a user inputs a command to start execution of thesequence of processes defined in the workflow, the informationprocessing system executes the processes in accordance with an orderdefined by the workflow. In order to execute the sequence of theprocesses, the user may select the predetermined workflow. The user maynot be required to select and execute the processes individually. Thus,the sequence of the processes can be efficiently executed.

FIG. 25 is a diagram showing an example of processes included in aworkflow. Here, the process 1 is a process of scanning an originaldocument, the process 2 is a process of data compression, the process 3is an optical character recognition (OCR) process, the process 4 is aPDF conversion process, and the process 5 is a mail sending process. Inmany cases, such a workflow is defined by an administrator of a user'saccount. The definition of the workflow may be made by combining suchprocesses. The user may select a desired workflow from a plurality ofworkflows that is defined in advance by the administrator (cf. PatentDocument 1 (Japanese Unexamined Patent Publication No. 2011-035779), forexample). Patent Document 1 discloses an image forming device thatdisplays names of defined workflows and processes included in thecorresponding workflows. Here, each of the workflows corresponds to theprocesses included in the workflow.

SUMMARY OF THE INVENTION

According to an aspect of the present invention, there is provided aprocess flow definition creating system configured to provide a processflow definition to a system for executing processes in an order inaccordance with the process flow definition for defining the processesto be executed by corresponding devices and the order of executing theprocesses. The process flow definition creating system includes a devicelist storage unit configured store a list of the devices; a screeninformation storage unit configured to store screen information, whereinthe screen information is for displaying a first field and a secondfield, the first field is for setting the processes in the order, andthe second field is for setting the devices that are to execute thecorresponding processes; a display control unit configured to parse thescreen information, and configured to display the parsed screeninformation; a setting reception unit configured to receive a settingfor the first field and a setting for the second field, wherein thesetting for the first field defines the processes and the order of theprocesses, and the setting for the second field defines correspondencebetween the processes and the devices that are to execute the processes;a definition creating unit configured to create the process flowdefinition, based on the order of the processes and the devicescorresponding to the processes that are received by the settingreception unit; and a definition storage unit configured to store theprocess flow definition.

According to another aspect of the present invention, there is provideda process flow definition creating device including a device liststorage unit configured store a list of devices; a screen informationstorage unit configured to store screen information, wherein the screeninformation is for displaying a first field and a second field, thefirst field is for setting processes in an order, and the second fieldis for setting the devices that are to execute the correspondingprocesses; a display control unit configured to parse the screeninformation, and configured to display the parsed screen information; asetting reception unit configured to receive a setting for the firstfield and a setting for the second field, wherein the setting for thefirst field defines the processes and the order of the processes, andthe setting for the second field defines correspondence between theprocesses and the devices that are to execute the processes; adefinition creating unit configured to create a process flow definition,based on the order of the processes and the devices corresponding to theprocesses that are received by the setting reception unit; a definitionstorage unit configured to store the process flow definition; and anetwork communication unit configured to transmit the process flowdefinition to a system for executing the processes in the order inaccordance with the process flow definition.

According to another aspect of the present invention, there is provideda method of creating a process flow definition, wherein the process flowdefinition is to be provided to a system for executing processes in anorder in accordance with the process flow definition, and the processflow definition defines the processes to be executed by correspondingdevices and the order of executing the processes. The method includesstoring a list of the devices; storing screen information, wherein thescreen information is for displaying a first field and a second field,the first field is for setting the processes in the order, and thesecond field is for setting the devices that are to execute thecorresponding processes; parsing the screen information, and displayingthe parsed screen information; receiving a setting for the first fieldand a setting for the second field, wherein the setting for the firstfield defines the processes and the order of the processes, and thesetting for the second field defines correspondence between theprocesses and the devices that are to execute the processes; creatingthe process flow definition, based on the order of the processes and thedevices corresponding to the processes that are received by thereceiving; and storing the process flow definition.

Other objects, features and advantages of the present invention willbecome more apparent from the following detailed description when readin conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram showing an example of correspondence betweenprocesses and devices;

FIGS. 2A-2D are diagrams schematically illustrating a procedure of anadministrator for defining a workflow;

FIGS. 3A and 3B are system configuration diagrams of examples of aninformation processing system;

FIG. 4 is a diagram showing an example of a hardware configuration of amultifunction peripheral (MFP) as an example of a workflowexecution/request device;

FIG. 5 is a diagram showing an example of a hardware configuration of aworkflow processing server, an administration server, and anadministrator's personal computer (PC);

FIG. 6 is a diagram showing an example of functional blocks of theadministration server and the administrator's PC;

FIG. 7A is a diagram showing an example of a device list table;

FIG. 7B is a diagram showing an example of a connection list database;

FIGS. 8A and 8B are diagrams showing examples of a process flowdefinition;

FIG. 9 is a diagram showing an example of the process flow definition inan XML format;

FIG. 10 is a diagram showing an example of functional blocks of theworkflow execution/request device (MFP) and the workflow processingserver;

FIG. 11 is a flowchart showing an example of a procedure of theadministrator's PC and the administration server for creating a processflow definition;

FIGS. 12A-12D are diagrams illustrating an example of the workflow;

FIGS. 13A-13C are diagrams illustrating an example of modifyingcorrespondence;

FIGS. 14A and 14B are diagrams showing an example of a correspondencescreen for a case where an administrator selects “to be linked withmodification of the correspondence;”

FIGS. 15A and 15B are diagrams showing an example of the correspondencescreen for a case where the administrator selects “not to be linked withmodification of the correspondence;”

FIGS. 16A and 16B are diagrams showing an example of the correspondencescreen for a case where the administrator selects “query as to whetheror not to modify the correspondence;”

FIGS. 17A and 17B are diagrams showing display examples for a case wherethe administrator defines correspondence between processes 1 to 5 andphysical devices;

FIG. 18 is a sequence diagram showing an example of a procedure of theinformation processing system for executing the workflow;

FIGS. 19A and 19B are diagrams showing examples of screens for selectingthe workflow;

FIG. 20 is a diagram showing another example of the schematicconfiguration of the information processing system;

FIGS. 21A and 21B are diagrams schematically illustrating examples ofthe workflow and the information processing system that executes theworkflow;

FIGS. 22A and 22B are diagrams illustrating an example of a process flowdefinition for polling;

FIG. 23 is a flowchart showing another example of the procedure of theadministrator's PC and the administration server for creating theprocess flow definition;

FIG. 24 is a sequence diagram showing another example of the procedureof the information processing system for executing the workflow; and

FIG. 25 is a diagram showing an example of processes included in theworkflow.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

A workflow can be executed, at least, by a single device. For example,all the processes included in a workflow may be executed by a singlemultifunction peripheral (MFP). However, in order to allow a workflow tobe executed by a single device, a process that cannot be processed bythe single device may not be included in a workflow. However, some usersmay wish to define a workflow by combining various types of processes.

Accordingly, a plurality of processes included in a workflow may beexecuted by a plurality of devices. When the plurality of processesincluded in the workflow is executed by the plurality of devices, anadministrator of the workflow may be required to do some work forassociating the processes with the devices. Such work can befacilitated, and operability for such work can be improved.

There is a need for a processing flow definition information creatingsystem that can provide a graphical user interface (GUI) with which aworkflow can be flexibly defined.

According to an embodiment of the present invention, a process flowdefinition creating system can be provided that may facilitate defininga workflow.

Hereinafter, the embodiment of the present invention is explained byreferring to the accompanying drawings. However, a technical scope ofthe present invention is not limited to the embodiment.

FIG. 1 is a diagram showing an example of correspondence betweenprocesses and devices. For example, the processes 1, 2, 4, and 5correspond to a multifunction peripheral (MFP), and the process 3corresponds to a server. An administrator of workflow may define thecorrespondence between the processes and the devices by using agraphical user interface (GUI).

FIGS. 2A-2D are diagrams schematically illustrating a procedure of theadministrator for defining a workflow by using an information processingsystem according to the embodiment. In FIG. 2A, selection of theprocesses 1 to 5 have already been made. Thus, the processes 1 to 5 areincluded in a single workflow. For each of FIGS. 2A-2D, the upper fieldof the figure may be referred to as “logical flow field” (or a firstfield), and the lower field of the figure may be referred to as“physical device flow field” (or a second field). The administrator mayperform an operation for defining correspondence between the devices(which are to execute the processes 1 to 5) and the processes 1 to 5.Hereinafter, the screen shown in each of FIGS. 2A-2D may be referred toas a correspondence screen. It is assumed that the correspondence screenis displayed on an administrator's personal computer (PC) 150.

FIG. 2A: A device list is displayed on the correspondence screen. Thedevice list may include an icon and/or a name of a physical device thatcan execute one or more of the processes 1 to 5. A user may drag anddrop a device icon 61 of a desired physical device to the physicaldevice flow field by operating a pointing device, such as a mouse or atouch panel. At this time, the administrator's PC 150 may automaticallydisplay device icons 61 of physical devices that can execute theprocesses 1 to 5 in the physical device flow field.

FIG. 2B: The administrator's PC 150 may connect each of process icons 62of the corresponding processes 1 to 5 and the device icon 61 by a line.The administrator can visually understand the correspondence between theprocesses 1 to 5 and the physical device, by confirming the lines thatconnect the physical device and the corresponding processes 1 to 5.

FIG. 2C: The administrator may wish to modify the correspondence. Forexample, for defining correspondence between the process 3 and aworkflow processing server 100, the administrator may drag and drop adevice icon 61 of the workflow processing server in the physical deviceflow field. Then, the administrator may drag from the process icon 62 ofthe process 3 to the device icon 61 of the workflow processing server100 by using the pointing device. In this manner, the correspondencebetween the process 3 and the MFP 201 can be switched to thecorrespondence between the process 3 and the workflow processing server100.

FIG. 2D: The administrator's PC 150 may connect the process icon 62 ofthe process 3 and the device icon 61 of the workflow processing server100 by a line. The administrator can visually understand that theprocess 3 corresponds to the workflow processing server 100 byconfirming the line that connects the process icon 62 of the process 3and the device icon 61 of the workflow processing server 100. Thecorrespondence between the MFP 201 and the processes 4 and 5 may be leftas it is. Alternatively, the correspondence between the MFP 201 and theprocesses 4 and 5 (i.e., the processes downstream of the process 3) maybe automatically switched to the correspondence between the workflowprocessing server 100 and the processes 4 and 5. Details are describedbelow.

In this manner, the information processing system 500 according to theembodiment can create a logical flow and a physical device flow on thesame screen. Accordingly, an administrator can visually definecorrespondence between a process and a physical device. Additionally oralternatively, the information processing system 500 can automaticallydefine correspondence between a process and a physical device. Thus, anamount of operations to be performed by an administrator can be reduced.Additionally, after correspondence between a process and a physicaldevice is automatically defined, the correspondence may be easilymodified.

Hereinafter, a person who defines a process flow definition is referredto as “administrator.” A person who executes a workflow is referred toas “user.”

Here, a “process flow definition” is information that defines aworkflow. The process flow definition may include at least the followinginformation: (i) an order of processes (e.g., the processes 1 to 5 ofFIGS. 2A-2D); (ii) devices that execute the processes; and (iii) jobsettings that may be required for the corresponding processes. A jobsetting may include, for example, a resolution and/or concentration ofscanning, and an e-mail address. A job setting may be defined by anadministrator, or by a user who executes a workflow.

Configuration Example

FIG. 3A is a diagram showing an example of a system configuration of theinformation processing system 500. A workflow execution/request device200, the workflow processing server 100, and an administration server250 are mutually connected through a network 400. Additionally, theadministrator's personal computer (PC) 150 can be connected to thenetwork 400.

The network 400 may be a local area network (LAN). Alternatively, thenetwork 400 may be a wide area network (WAN) in which a plurality ofLANs is connected through corresponding routers. The Internet may beconsidered as an example of the network 400, provided that a firewallmay not be required. The network 400 may achieved by a wired line.Alternatively, a portion of or all the network 400 may be achieved by awireless LAN (e.g., IEEE 802.11b/a/g/n). Additionally, a mobilecommunication network, such as a cellular phone network, a WiMAX-basednetwork, or a PHS network, may be considered as an example of thenetwork 400. Here, an ad-hoc network may also be considered as anexample of the network 400. In the ad-hoc network, the devices includedin the information processing system 500 are connected in a peer-to-peermanner by using an ad-hoc mode of the wireless LAN.

The workflow execution/request device 200 can execute a workflow byitself. The workflow execution/request device 200 can request theworkflow processing server 100 to execute a workflow. In FIG. 3A, a MFP201, a mobile terminal 202, and a client terminal 203 are depicted. Aninformation processing device that includes a communication function,such as the MFP 201, the mobile terminal 202, or the client terminal203, can be the workflow execution/request device 200. The informationprocessing system 500 may include one or more workflow execution/requestdevices 200. The MFP 201 is a device that includes a function forforming an image, such as a copier, a scanner, a printer, or a facsimilemachine. The MFP 201 may include at least one of the functions of theabove-described devices (i.e., the copier, the scanner, the printer, andthe facsimile machine). The MFP 201 may process image data as job data.Here, the image data may be created by scanning an original document,for example. The MFP 201 may transmit the processed job data to theworkflow processing server 100, together with the process flowdefinition.

The mobile terminal 202 is a terminal that can be carried or held by auser, such as a mobile phone, a smart phone, a tablet terminal, apersonal digital assistant (PDA), or a digital camera. The mobileterminal 202 may transmit, for example, image data, which may be jobdata that is captured by a camera of the mobile phone or the digitalcamera, and a process flow definition to the workflow processing server100.

The client terminal 203 is an information processing device that can beused by a user, such as a laptop PC, a desktop PC, a work station, or avideo conference terminal. The client terminal 203 may transmitapplication data created by an application and/or web data retrievedfrom a web server, as job data, to the workflow processing server 100,together with a process flow definition, for example.

Here, the workflow execution/request device 200 is assumed to be adevice that is directly operated by a user. However, job data may not becreated or stored by such a device that is directly operated by a user.For example, the client terminal 203 may specify job data stored in anetwork attached storage (NAS) or the like, and the client terminal 203may cause the NAS or the like to transmit the job data to the workflowprocessing server 100.

The workflow processing server 100 is an information processing device,such as a PC, a server, or a thin client. The MFP 201 can be theworkflow processing server 100. The workflow processing server 100 canexecute one or more sequences of processes included in a workflow. Theinformation processing system 500 may include one or more workflowprocessing servers 100. When the workflow processing server 100 receivesjob data and a process flow definition from the workflowexecution/request device 200, the workflow processing server 100 mayapply an OCR process to the job data, and the workflow processing server100 may transmit an e-mail including the processed job data, inaccordance with the process flow definition, for example.

The administration server 250 may receive a definition of a workflowfrom the administrator's PC 150. The administration server 250 may storeone or more process flow definitions that are defined by anadministrator. The administration server 250 may transmit a process flowdefinition in response to a request from the flow execution/requestdevice 200. A user can select a workflow to be executed from a list ofworkflows.

As described above, an input process may be mainly executed by theworkflow execution/request device 200. A conversion process may bemainly executed by a combination of the workflow execution/requestdevice 200 and the workflow processing server 100. An output process maybe mainly executed by the combination of the workflow execution/requestdevice 200 and the workflow processing server 100.

The job data to be input may be based on a physical medium, such as anoriginal document. Alternatively, the job data to be input may be basedon electronic data, such as data created by a word processor. The outputmay be based on a physical medium, such as an image printed on a papersheet. Alternatively, the output may be based on electronic data, suchas electronic data stored in a document box, or electronic data includedin an e-mail.

FIG. 3B is a diagram showing another example of the system configurationof the information processing system 500. As shown in FIG. 3B, the workflow execution/request device 200 and a workflow server 260 areconnected through the network 400. The workflow server 260 includes thefunction of the workflow processing server 100 and the administrationserver 250 of FIG. 3A. Accordingly, the workflow server 260 can storeprocess flow definitions. In addition, the workflow server 260 canexecute a workflow. The system configuration of the informationprocessing system 500 can be that of FIG. 3A or that of FIG. 3B. In thefollowing, the embodiment is explained based on the system configurationshown in FIG. 3A.

FIG. 4 is a diagram showing an example of a hardware configuration ofthe MFP 201 as an example of the workflow execution/request device 200.The MFP 201 may include a controller 130; an operations panel 125; afacsimile control unit (FCU) 126; a capturing unit 127; and a printingunit 128.

The controller 130 may include a CPU 114; an ASIC 116; a north bridge(NB) 115; a south bridge (SB) 117; a system memory (MEM-P) 111; a localmemory (MEM-C) 112; a hard disk drive (HDD) 113; a memory card slot 123;a network interface controller 118; a USB device 119; an IEEE 1394device 121; and a Centronics device 122.

The CPU 114 is an integrated circuit (IC) for executing various types ofinformation processing. The CPU 114 can execute an application that runson an operating system (OS) or on a platform. The CPU 114 can executethe application in a parallel manner on a process-by-process basis. TheASIC 116 is an IC for image processing. The NB 115 is a bridge forconnecting the CPU 114 and the ASIC 116. The SB 117 is a bridge forconnecting the NB 115 to a peripheral device or the like. The ASIC 116and the NB 115 can be connected through an accelerated graphics port(AGP), for example.

The MEM-P 111 is a memory that is connected to the NB 115. The MEM-C 112is a memory that is connected to the ASIC 116. The HDD 113 is a storagedevice that is connected to the ASIC 116. The HDD 113 can be used forstoring, for example, image data, document data, programs, font data,and/or form data. The HDD 113 stores various types of applicationprograms (e.g., programs of a copy application, a scanner application, aprinter application, and a facsimile application) and a program 131. Theprogram 131 is for receiving a definition of a workflow defined by auser.

The memory card slot 123 is connected to the SB 117. The memory cardslot 123 is used for attaching (inserting) a memory card 124 to the MFP201. The memory card 124 is a flash memory, such as a USB memory or a SDmemory. The memory card 124 can be used for loading the program 131.Alternatively, the program 131 may be downloaded from a predeterminedserver to the MFP 201.

The NIC 118 is a controller for executing data communication through thenetwork 400, for example. A MAC address may be used for the datacommunication. The USB device 119 is a device that provides a serialport conforming to the USB standard. The IEEE 1394 device 121 is adevice that provides a serial port conforming to the IEEE 1394 standard.The Centronics device 122 is a device that provides a parallel portconforming to the Centronics specification. The NIC 118, the USB device119, the IEEE 1394 device 121, and the Centronics device 122 areconnected to the NB 115 and to the SB 117 through a peripheral componentinterconnect (PCI) bus.

The operations panel 125 is a hardware component (an operation unit) fora user to make an input to the MFP 201. At the same time, the operationspanel 125 is a hardware component (a display) for the MFP 201 to displaya menu screen. The operations panel 125 is connected to the ASIC 116.The FCU 126, the capturing unit 127, and the printing unit 128 areconnected to the ASIC 116 through a peripheral component interconnect(PCI) bus.

The capturing unit 127 is for generating color digital data ormonochrome digital data (which may be referred to as “image data,”hereinafter). The capturing unit 127 optically scans an originaldocument disposed on contact glass. The capturing unit 127 applies ananalog-to-digital (A/D) conversion process to the reflected light. Then,the capturing unit 127 generates the image data by applying imageprocessing to the resultant data.

The printing unit 128 may include a tandem type photosensitive drum, forexample. The printing unit 128 can modulate a laser beam based on theabove-described image data or based on page description language (PDL)data received from a user's PC. The printing unit 128 can form a latentimage by scanning the modulated laser beam onto the photosensitive drum.The printing unit 128 can develop an image by applying toner onto thelatent image. Here, the image is for one page. The printing unit 128 cantransfer the image onto a paper sheet by using heat and pressure. Here,an electrophotographic plotter is explained as an example of theprinting unit 128. However, the printing unit 128 is not limited to thisexample. For example, the printing unit 128 may be an inkjet plotterengine that forms an image by discharging liquid droplets.

The FCU 126 can establish connection to the network 400 through the NIC118. In this case, the FCU 126 may communicate image data in accordancewith a communication protocol conforming to T.37 standard or T.38standard, for example. Alternatively, the FCU 126 can establishconnection to a public telecommunication network. In this case, the FCU126 may communicate image data in accordance with a communicationprotocol conforming to G3 standard or G4 standard, for example. Even ifimage data is received while a power supply of the MFP 201 is turnedoff, the FCU 126 can activate the printing unit 128, and the FCU 126 cancause the printing unit 128 to print the image data onto a paper sheet.

FIG. 5 is a diagram showing an example of a hardware configuration ofthe workflow processing server 100, the administration server 250, andthe administrator's PC 150. Each of the workflow processing server 100,the administration server 250, and the administrator's PC 150 mayinclude a CPU 301; a ROM 302; a RAM 303, a HDD 304, a graphics board 305to which a display 320 is connected; a keyboard and mouse 306; a mediadrive 307; and a network communication unit 308. The CPU 301 may loadthe program 310 stored in the HDD 304 into the RAM 303, and the CPU 301may execute the program 310. In this manner, the CPU 301 can execute aninput process, an output process, and/or data processing by controllingcorresponding components. The ROM 302 may store the Basic Input/OutputSystem (BIOS) and/or a starting program for reading out a bootstraploader from the HDD 304 and writing the bootstrap loader in the RAM 303.The bootstrap loader reads out an operating system (OS) program from theHDD 304, and the bootstrap loader writes the operating system program inthe RAM 303.

Here, the HDD 304 is used as a non-volatile memory. However, thenon-volatile memory is not limited to the HDD 304. For example, a solidstate drive (SSD) may be used, instead of the HDD 304. The HDD 304stores the OS, a device driver, and the program 310. The program 310 isfor providing a function described below. The display 320 displays a GUIscreen. The GUI screen may be created by the graphics board 305 undercontrol of a program.

The keyboard and mouse 306 is an input device for receiving a user'soperation. The media drive 307 may read and write data in an opticalmedium, such as a compact disk, a DVD, or a Blu-ray Disc. Additionally,the media drive 307 may read and write data in a flash memory. Thenetwork communication unit 308 may be an Ethernet (registered trademark) card for establishing connection to a LAN, for example. Protocolprocessing of the TCP/IP (and/or UDP/IP) and an application layer may beexecuted by the OS and/or by the program 310. There are many types ofapplication layer protocols. For example, the Simple Network ManagementProtocol (SNMP), the HTTP, the FTP, the Server Message Block (SMB) canbe considered as examples of the application layer protocol.

The program 310 may be stored in a computer readable recording medium asa file in an installable format or in an executable format. Accordingly,the program 310 may be distributed by distributing the computer readablerecording medium storing the program 310. Alternatively or additionally,the program 310 may be distributed by a server (not shown) as a file inan installable format or in an executable format.

[Function, Table]

FIG. 6 is a diagram showing an example of functional blocks of theadministration server 250 and the administrator's PC 150. Theadministrator's PC 150 may include a screen data request unit 51; anoperation reception unit 52; a display controller 53; and a process flowdefinition transmitter 54. The operation reception unit 52 receives auser's operation on the keyboard and mouse 306. The screen data requestunit 51 requests to the administration server 250 for screen data. Thedisplay controller 53 may be a browser application, for example. Thedisplay controller 53 parses screen data, and the display controller 53can displays the parsed screen data on the display 320. The screendisplayed on the display 320 may be a correspondence screen. A processflow definition can be defined by receiving, through the operationreception unit 52, an administrator's operation on the correspondencescreen displayed on the display 320. The process flow definitiontransmitter 54 transmits the process flow definition that is defined bythe administrator to the administration server 250.

The administration server 250 may include a screen data database 44; adevice list table 45; a workflow list database 38; a connectioninformation database 46; a screen data transmitter 41; a process flowdefinition receiver 42; and a process flow definition creating unit 43.The screen data database 44 stores screen data described in HTML,JavaScript (registered trademark), and/or XML, for example. The devicelist table 45 registers a list of physical devices that can execute aprocess. The workflow list database 38 registers a list of workflowsthat are defined by an administrator. Here, a physical device is anelement included in the information processing system 500 that canexecute a workflow. Specifically, a physical device may be the workflowexecution/request device 200 or the workflow processing server 100.

When the administration server 250 receives a request from theadministrator's PC 150, the screen data transmitter 41 retrieves screendata from the screen data database 44, and the screen data transmitter41 transmits the retrieved screen data to the administrator's PC 150.The process flow definition receiver 42 receives a process flowdefinition from the administrator's PC 150. The process flow definitionreceiver 42 outputs the received process flow definition to the processflow definition creating unit 43. The process flow definition creatingunit 43 completes (creates) the process flow definition by referring tothe connection information database 46, and the process flow definitioncreating unit 43 registers the completed (created) process flowdefinition in the workflow list database 38. Here, data that is the sameas the data stored in the workflow list data base 38 may be stored inthe workflow processing server 100 and/or in the MFP 201.

FIG. 7A is a diagram showing an example of the device list table 45. Thedevice list table 45 registers information of processes, information ofdevices that can execute the processes, and machine identifications(IDs) that identifies the corresponding devices. Here, in the devicelist table 45, the information of the processes corresponds to theinformation of the devices and the machine IDs. A machine ID isidentifying information that uniquely identifies a physical device inthe information processing system 500. The device list table 45 istransmitted to the administrator's PC 150 together with the screen data.With the device list table 45, the administrator's PC 150 can avoidmismatch between the process and the physical device.

FIG. 7B is a diagram showing an example of the connection informationdatabase 46. The connection information database 46 registers IPaddresses of connection destination physical devices and authenticationinformation. With these IP addresses, when a single workflow is to beexecuted by a plurality of physical devices, for example, the MFP 201can transmit a process flow definition and job data to the workflowprocessing server 100. In the above-described example, the connectioninformation database 46 registers the IP addresses. However, theconnection information database 46 according to the embodiment is notlimited to this. For example, the connection information database 46 mayregister machine IDs, instead of the IP addresses. In this case, theconnection information database 46 may query a Domain Name System (DNS)server for an IP address, based on the machine ID. In this manner, theconnection information database 46 may identify the IP address based onthe machine ID. The authentication information is information that isused by a physical device (e.g., the MFP 201 or the workflow processingserver 100) to authenticate a user. For example, authenticationinformation used by the MFP 201 may be a user name and a password.Authentication information used by the workflow processing server 100may be an administrator name and a password. For executing a workflow,the workflow execution/request device 200 queries a user for validauthentication information.

FIGS. 8A and 8B are diagrams showing examples of the process flowdefinition. FIG. 8A shows the examples of the process flow definitionfrom a viewpoint of an administrator or a user. FIG. 8B shows theexample of the process flow definition that is created by theadministration server 250. In FIG. 8B, the workflows 2 and 3 areomitted. Immediately after a process flow definition is transmitted fromthe administrator's PC 150 to the administration server 250, the processflow definition is in a state shown in FIG. 8A.

As shown in FIG. 8A, the workflow list database 38 registers processflow definitions of corresponding workflows. Specifically, for each ofthe workflow names (e.g., the workflow 1, the workflow 2, or theworkflow 3), an order of a sequence of processes and the devicescorresponding to the processes are registered. Here, a number ofprocesses included in a single workflow may be greater than or equal tofive. Alternatively, a number of processes included in a single workflowmay be less than five. A single work flow may be defined only to includeone process. In FIG. 8A, the job settings (i.e., the information (iii)described above) of the corresponding processes are omitted.

The process flow definition creating unit 43 completes (creates) theprocess flow definition as shown in FIG. 8B by inserting some connectionprocesses into the process flow definition transmitted from theadministrator's PC 150. As described in detail below, when a physicaldevice to execute a process is to be switched, a connection process isinserted into a corresponding portion of a process flow definition. InFIG. 8B, the process 2-1 and the process 3-1 are connection processes.

FIG. 9 is a diagram showing an example of a process flow definition inXML format. The lines from <flows> to </flows> define a single workflow.The lines from <flow> to </flow> define an order of the processes in theworkflow.

A single process is described in units of a <plugin id> tag. The <pluginid> tag described a type of the process to be executed. For example,plugin id=“SCAN” represents a process of reading an original document,and type=“input” represents that a type of data processing is an inputprocess. Similarly, displayName=“Scanning” represents a name of aprocess that can be visually confirmed by a user on the administrator'sPC 150 or on the operations panel 125. Similarly,proceed=machineID_(—)001 represents a machine ID of a physical devicethat corresponds to the process.

Similarly, plugin id=“Compression” represents a process of datacompression, plugin id=“Connect” represents a connection process, pluginid=“OCR” represents an OCR process, plugin id=“PDFConverter” representsa PDF conversion process, and plugin id=“MailSend” represents a mailsending process. Further, type=“filter” represents that a type of dataprocessing is a conversion process, type=“output” represents that a typeof data processing is an output process, and type=“send” represents atransmission process for a connection process, which is neither aconversion process nor an output process.

The lines from <parameter> to </parameter> defines a job setting. Thejob setting describes settings that may be required for a correspondingprocess. Some job settings can be defined by an administrator or a user.Some job settings may be determined in advance as corresponding fixedvalues.

The <current_point> tag represents a process of a workflow that is to becurrently executed (e.g., upon receiving the process flow definition, orimmediately after update) by a physical device. Hereinafter, “currentpoint” may be referred to as a “current point.” The MFP 201 or theworkflow processing server 100 determines a process to execute byreferring to the current point. When a process is completed, content ofthe current point is updated to be a succeeding process to be executed.For example, when a scanning process is completed, the <current_point>tag is updated as shown below.

<current_point> <plugin id=“Compression” /> </current_point>

FIG. 10 a diagram showing an example of functional blocks of theworkflow execution/request device 200 (e.g., the MFP 201) and theworkflow processing server 100. The workflow execution/request device200 may include a log-in unit 37 and a process flow definition selectionunit 36. The log-in unit 37 may query authentication information thatmay be required for executing a workflow. The authentication informationmay be log-in information for logging in to the MFP 201 operated by auser, for example. In other words, a user that can log in to the MFP 201is allowed to execute a workflow. In this case, when a physical deviceis to be switched to another physical device, the other physical devicerefers to the connection information database 46, and retrieves requiredauthentication information from the connection information database 46.The other physical device attaches the retrieved authenticationinformation to the process flow definition. For a case whereauthentication information is strictly required, the log-in unit 37 mayquery a user for authentication information of each of physical devicesthat executes a corresponding process included in a workflow.

A user can make a selection of a workflow by using the process flowdefinition selection unit 36. The process flow definition selection unit36 receives the selection of the workflow made by the user. When the MFP201 is used within an office, the MFP 201 may obtain the workflow listdatabase 38 from the administration server 250 in advance. A user maycause the MFP 201 to display a list of workflows on the operations panel125 by a predetermined operation. Then, the user may select a desiredworkflow. When the workflow execution/request device 200 is the mobileterminal 202, for example, the mobile terminal 202 (as the workflowexecution/request device 200) may access the administration server 250or the workflow processing server 100, and the mobile terminal 202 mayretrieve a list of workflows registered in the workflow list database38.

The process flow definition selection unit 36 queries, for each processincluded in the workflow selected by the user, a required job setting.For example, for an input process, a setting of a resolution and/orconcentration (density) that can be set for scanning may be queried. Fora conversion process, for example, a compression ratio may be queried.For an output process (printing), a setting of an e-mail address may bereceived, for example. When an input is based on electronic data, asetting of job data (e.g., document data, image data, and/or video data)to be processed may be received. When an output is based on printing ona physical medium, such as a sheet of paper, a setting of a size of asheet, magnification/reduction, aggregation printing (N in 1 printing),color/monochrome, a number sheets to be printed, a finish, and/or thelike may be received. The process flow definition selection unit 36updates the process flow definition with the job settings of thecorresponding process.

As for functions related to execution of a workflow, the MFP 201 (i.e.,the workflow execution/request device 200) may include one ore moreplug-ins 21; a flow control unit 22; and a job controller 23. The jobcontroller 23 controls execution of each of processes of the workflow.First, a job receiver 33 of the job controller 23 retrieves a processflow definition from the process flow definition selection unit 36.Subsequently, by executing an input process, job data is obtained. Theprocess flow definition is stored in a job queue 35 of the jobcontroller 23 together with the job data.

A process flow definition and job data may be transmitted from anotherphysical device. In other words, the MFP 201 (i.e., the workflowexecution/request device 200) may receive a process flow definition andjob data from the workflow processing server 100. (Additionally, theworkflow processing server 100 may receive a process flow definition andjob data from the MFP 201 (i.e., the workflow execution/request device200).) In such a case, the job controller 23 stores the process flowdefinition and the job data in the job queue 35. Here, a single job maycorrespond to a single process to which a single plug-in is attached.

The job receiver 33 determines whether the job data is to be processedby the MFP 201 (i.e., the workflow execution/request device 200), basedon the process flow definition of the workflow that is temporarilystored in the job queue 35. Namely, the job receiver 33 determineswhether the process of the current point corresponds to the machine IDof the MFP 201 (i.e., the workflow execution/request device 200) itself.Even if the process of the current point corresponds to the machine IDof the MFP 201 (i.e., the workflow execution/request device 200) itself,if Plugin id=“Connect” is specified, the process is a connectionprocess. Accordingly, in this case, a job execution unit 31 of the jobcontroller 23 updates the process flow definition, and subsequently thejob execution unit 31 causes a job transmitter 32 of the job controller23 to transmit the process flow definition and the job data. Thedestination of the transmission is described in the process flowdefinition.

When the process of the current point corresponds to the machine ID ofthe MFP 201 (i.e., the workflow execution/request device 200) itself,and when the process of the current point is not a connection process,the job execution unit 31 reads out the process flow definition and thejob data from the job queue 35, and the job execution unit 31 executesthe process defined by the process flow definition and the job data. Thejob execution unit 31 outputs the process flow definition and the jobdata to the flow control unit 22.

The flow control unit 22 selects a plug-in 21 in accordance with theprocess flow definition. As described above, a plug-in 21 may be aplug-in for executing an input process, a plug-in for executing a PDFconversion process, a plug-in for sending an e-mail, a plug-in forexecuting an OCR process, a plug-in for executing a translation process,or a plug-in for executing an output process, for example. Each of theplug-ins 21 can operate on a common platform. The MFP 201 (i.e., theworkflow execution/request device 200) and the workflow processingserver 100 can independently add a single plug-in 21, or canindependently remove a single plug-in 21. A plug-in 21 does notinterfere with processing of another plug-in 21. In this example, it isexplained that a process may be executed by a plug-in 21. However, theembodiment is not limited to this. For example, a process may beexecuted by an application program.

The flow control unit 22 identifies the process of the current point.Then, the flow control unit 22 calls a plug-in 21 that is to execute theprocess, and the flow control unit 22 causes the plug-in 21 to executethe process. When the job is successfully completed, the flow controlunit 22 updates the process of the current point. The flow control unit22 stores the process flow definition and the job data in the job queue35.

A job detection unit 34 of the job controller 23 detects that the job isinput to the job queue 35. Namely, when job data that is created by theplug-in by executing a single process is stored in the job queue 35, thejob detection unit 34 detects that the job data is stored in the jobqueue 35. After that, the job execution unit 31 and the like repeatsimilar processes.

The workflow processing server 100 may include one ore more plug-ins 21;a flow control unit 22; and a job controller 23. As for execution of ajob, the workflow processing server 100 may include the same functionsas those of the MFP 201 (i.e., the workflow execution/request device200). In other words, an execution procedure of a workflow by theworkflow processing server 100 may be the same as that of the MFP 201(i.e., the workflow execution/request device 200).

Accordingly, even if a process is to be processed across the MFP 201 andthe workflow processing server 100, a corresponding workflow can beprocessed because a process flow definition and job data arecommunicated through a connection process. Namely, a workflow can beflexibly defined.

[Operation Procedure of Creating a Process Flow Definition]

FIG. 11 shows a flowchart of an example of a procedure for theadministrator's PC 150 and the administration server 250 to create aprocess flow definition.

When the screen data request unit 51 of the administrator's PC 150queries the administration server 250 for screen data of thecorrespondence screen, the screen data transmitter 41 of theadministration server 250 transmits the screen data to theadministrator's PC 150 (S210).

The screen data request unit 51 receives the screen data (S110).

The display controller 53 parses the screen data, and the displaycontroller 53 displays the correspondence screen on the display 320(S120).

A user sets one ore more processes in the logical flow field byoperating the keyboard and mouse 306 (S130).

Next, the user defines correspondence between the processes in thelogical flow field and physical devices by operating the keyboard andmouse 306 (S140). Details of the procedure are explained by referring toFIGS. 12 to 17.

The process flow definition transmitter 54 transmits the process flowdefinition to the administration server 250 (S150).

The process flow definition receiver 42 of the administration server 250receives the process flow definition (S220).

The process flow definition creating unit 43 determines whether theprocess flow definition includes a process for which a physical deviceis to be switched to another physical device that is to execute theprocess (S230). Namely, a determination is made as to whether theprocess flow definition includes a process for which the MFP 201 is tobe switched to the workflow processing server 100, or for which theworkflow processing server 100 is to be switched to the MFP 201.

When the process flow definition does not include a process for which aphysical device is to be switched to another physical device that is toexecute the process (S230: No), the process flow definition creatingunit 43 registers the process flow definition in the workflow listdatabase 38 without updating the process flow definition (S250).

When the process flow definition includes a process for which a physicaldevice is to be switched to another physical device that is to executethe process (S230: Yes), the process flow definition creating unit 43inserts a connection process immediately prior to the process for whichthe physical device is to be switched to the other physical device(S240). Then, the process flow definition creating unit 43 registers theupdated process flow definition in the workflow list database (S250).Here, as shown in FIG. 9, “plugin id” of the connection process isdefined to be “Connect” in advance, and “type” of the connection processis defined to be “send” in advance. The connection process is not to bedisplayed. Accordingly, for the connection process, “displayName” is notdefined (i.e., the corresponding field is blank). The field “proceed”defines the physical device for executing the connection process, whichis the device that is to execute the process immediately prior to theconnection process. The process flow definition creating unit 43 readsout an IP address corresponding to the physical device (i.e., aconnection destination) that is to execute the process subsequent to theconnection process from the connection information database 46, and theprocess flow definition creating unit 43 writes the IP address in thejob setting (i.e., in the field of <parameter>) of the connectionprocess. In this manner, by using the connection information database46, a connection process can be easily inserted.

In the above example, a case is explained where the administrationserver 250 and the administrator's PC 150 communicate and define theprocess flow definition. However, the embodiment is not limited to this.For example, the administrator's PC 150 may be a standalone PC, and aprocess flow definition may be created by the administrator's PC 150itself. In such a case, the administrator's PC 150 may include thescreen data transmitter 41; the process flow definition receiver 42; theprocess flow definition creating unit 43; the screen data base 44; thedevice list table 45; the connection information database 46; and theworkflow list database 38, in addition to the screen data request unit51; the operation reception unit 52; the display controller 53; and theprocess flow definition transmitter 54. Additionally, the networkcommunication unit 308 of the administrator's PC 150 may provide aprocess flow definition to a system that sequentially executes processesdefined by the process flow definition through the network 400.

[Example of a Process Flow Definition]

FIGS. 12A-12D are diagrams illustrating an example of a process flowdefinition. FIG. 12A shows an example of an initial condition of thecorrespondence screen. An administrator sets processes in a logical flowfield that is the upper side of the correspondence screen. Theadministrator defines devices that execute corresponding processes in aphysical device flow field that is the lower side of the correspondencescreen. In the correspondence screen, a process list and a device listare displayed. The device icons 61 of the device list are based oninformation of the physical devices stored in the device list table 45.The process icons 62 of the process list are based on information of theprocesses stored in the device list table 45. The processes 1 to 5 ofthe process list can actually be displayed in such a manner that theprocess names, such as an OCR process or a PDF conversion process, canbe recognized.

In the initial condition, in the upper side of the correspondence table(i.e., the logical flow field), “process 1” is displayed while beingblinked, for example. This is for explicitly indicating a position wherethe administrator is to drag and drop a process icon 62 of the processlist. Alternatively, the administrator may arrange the process icons 62in a desired order, or only a box for setting the process icons 62 maybedisplayed, without supporting an input operation. In a server-clientenvironment, an operation, such as dragging of an icon, may be enabledfor a rich client environment. For example, such an operation can beachieved by combining a Canvas tag of HTML 5 and JavaScript. As shown inFIG. 12A, when the administrator selects a process, and drags theselected process to the position of “process 1” in the logical flowfield, the first process is defined.

After the process 1 is defined by the administrator, a device icon 61can be selected in the device list. The display controller 53 cancontrol the correspondence screen, so that only the device icons 61 ofthe physical devices that can execute the process 1 can be selected inthe device list. Additionally, when there is only one physical devicethat can execute the process 1, the display controller 53 can cause thedevice icon 61 of the device that can execute the process 1 to beautomatically displayed in the physical device flow field, even if theadministrator does not operate the correspondence screen. Hereinafter,such automatic arrangement of a device icon 61 is referred to as“automatic arrangement.” When the automatic arrangement is executed, theprocess icon 62 and the device icon 61 can be automatically connectedwith a line.

As shown in FIG. 12B, when the administrator selects a process and dragsthe selected process into the logical flow field, the second process isdefined. The display controller 53 displays an arrow at a positiondownstream the process 1, and the display controller 53 displays theprocess icon 62 of the process 2 at a predetermined position. Theadministrator defines a logical flow by repeating such an operation.After defining the process 2, the administrator drags the device icon 61of the MFP 201 into the physical device flow field.

The administrator may arrange a device icon 61 prior to arranging aprocess icon 62. When a device icon 61 is arranged in the physicaldevice flow field, and when the administrator arranges a process icon 62in the logical flow field, it is possible that the process representedby the process icon 62 cannot be executed by the physical devicerepresented by the device icon 61. In such a case, the displaycontroller 53 replaces the device icon 61 in the physical device flowfield with another device icon 61 of the physical device that canexecute the process represented by the process icon 62.

As shown in FIG. 12C, when the administrator arranges the device icon 61in the physical device flow field, the process icons 62 and the deviceicon 61 are connected with the corresponding lines. In this manner, thedevice icon 61 of the MFP 201 and the process icons 62 of the processes1 and 2 are connected with the corresponding lines. FIG. 12D shows thecorrespondence screen to which the administrator adds the process 3.When the administrator adds the process icon 62 representing the process3 to the logical flow field, the display controller 53 automaticallyapplies the correspondence between the physical device and the precedingprocess to the added process 3. In other words, the display controller53 defines correspondence between the process 3 and the MFP 201 becausethe process 2 corresponds to the MFP 201. In this manner, theadministrator can define the correspondence between the process 3 andthe physical device with fewer steps.

Consequently, an administrator can define correspondence between asingle physical device and a plurality of processes only by draggingprocess icons 62 into the logical flow field.

FIGS. 13A-13C are diagrams illustrating an example of modifying thecorrespondence. As shown in FIG. 13A, the processes 1 to 5 correspond tothe MFP 201. When the administrator wishes to define correspondencebetween some of the preprocess 1 to 5 and another physical device, theadministrator drags a device icon 61 of the other device into thephysical device flow field, as shown in FIG. 13A.

FIG. 13B shows the correspondence screen in which the device icon 62 ofthe workflow processing server 100 is added to the physical device flowfield. At this moment, the display controller 53 does not modifyanything because the process for which the correspondence is to bemodified is not identified. Furthermore, for example, whencorrespondence between the process 3 and the workflow processing server100 is to be defined, the administrator's PC 150 may not determinewhether only the correspondence between the process 3 and the physicaldevice is to be modified or the correspondence between the processes 3to 5 and the physical device is to be modified.

Accordingly, the display controller 53 displays a dialog box forreceiving a selection of a method of modifying the correspondence. Thisdialog box can be displayed at the timing of adding the device icon 61as shown in FIG. 13B. Additionally, this dialog box can be displayed bythe administrator at desired timing.

FIG. 13C is a diagram showing an example of the dialog box. For thedescription “correspondence of the subsequent logical flow” in thedialog box, one method of modification can be selected amongst threealternative methods of modification, which are “to be linked withmodification of the correspondence,” “not to be linked with modificationof the correspondence,” and “query as to whether or not to modify thecorrespondence.” The administrator may click a radio button byconsidering necessity to modify the physical device for the subsequentprocesses 4 and 5.

-   -   “to be linked with modification of the correspondence”

FIG. 14A is a diagram showing an example of the correspondence screenfor a case in which the administrator selects “to be linked withmodification of the correspondence.” The administrator definescorrespondence between the process 3 and the workflow processing server100. The correspondence may be defined by dragging from the process icon62 of the process 3 in the logical flow field to the device icon 61 ofthe workflow processing server 100. Alternatively, the correspondencemay be defined by connecting the process icon 62 of the process 3 andthe device icon 61 of the workflow processing server 100 by a dashedline in the correspondence screen.

FIG. 14B is a diagram showing an example of the correspondence screenafter the correspondence is modified. In accordance with themodification of the correspondence of the process 3, the correspondencebetween the physical device and the processes 4 and 5 is modified fromthe correspondence between the MFP 201 and the processes 4 and 5 to thecorrespondence between the workflow processing server 100 and theprocesses 4 and 5.

-   -   “not to be linked with modification of the correspondence”

FIG. 15A is a diagram showing an example of the correspondence screenfor a case in which the administrator selects “not to be linked withmodification of the correspondence.” FIG. 15B is a diagram showing anexample of the correspondence screen after the correspondence ismodified. After the correspondence of the process 3 is modified, theprocesses 4 and 5 still correspond to the MFP 201 because “not to belinked with modification of the correspondence” is selected. In thiscase, the display controller 53 displays the device icon 61 of the MFP201 at a position downstream the device icon 61 of the workflowprocessing server 100. The display controller 53 connects the deviceicon 61 of the MFP 201 to the process icons 62 of the processes 4 and 5with corresponding lines.

-   -   “query as to whether or not to modify the correspondence”

FIG. 16A is a diagram showing an example of the correspondence screenfor a case in which the administrator selects “query as to whether ornot to modify the correspondence.” FIG. 16B shows an example of a dialogbox for query. When “query as to whether or not to modify thecorrespondence” is selected, and when a device icon 61 is added to thephysical device flow field and the correspondence between the process 3and the device icon 61 of the workflow processing server 100 is defined,the display controller 53 display this dialog box.

The dialog box displays “please check a radio button of a process thatis to correspond to the physical device “workflow processing server,”and press the OK button.” Additionally, a “select all” button and a“release all” button are displayed. The processes 4 and 5 that aresubsequent to the process 3 are displayed with corresponding checkboxes. The administrator can select a method of defining thecorrespondence of the workflow processing server 100 (i.e., a method ofmodifying the correspondence), for example, by selecting the “selectall” button, or by clicking the corresponding check box.

-   -   color coding display after defining the correspondence

FIG. 17A is a diagram showing a display example of the correspondencescreen after the administrator defines the correspondence between theprocesses 1 to 5 and the physical devices. In FIG. 17A, the area wherethe process icons 62 of the processes 1 and 2 and the device icon 61 ofthe MFP 201 are arranged is filled with a single color. The area wherethe process icon 62 of the process 3 and the device icon 61 of theworkflow processing server 100 are arranged is filled with a singlecolor that is different from the color of the area of the processes 1and 2. The area where the process icons 62 of the processes 4 and 5 andthe device icon 61 of the MFP 201 are arranged is filled with the samecolor as the color of the area of the processes 1 and 2. Namely, whencorrespondence is defined between a process and a physical device, anarea where a process icon 62 of the process and a device icon 61 of thephysical device are arranged is filled with the same single color.Namely, an administrator can easily visualize correspondence between aprocess and a physical device by the color coding.

FIG. 17B is a diagram showing another display example of thecorrespondence between the processes 1 to 5 and the physical devices. InFIG. 17A, the areas other than the areas of the icons are filled withthe corresponding colors. In FIG. 17B, the icons are filled withcorresponding colors. In other words, the process icons 62 of theprocesses 1 and 2 are filled with a single color that is the same coloras the color of the device icon 61 of the MFP 201. The process icon 62of the process 3 and the device icon 61 of the workflow preprocessserver 100 are filled with a single color that is different from thecolor of the process icons 62 of the processes 1 and 2. The processicons 62 of the processes 4 and 5 and the device icon 61 of the MFP 201are filled with the same color as the color of the process icons 62 ofthe processes 1 and 2. With such color coding, correspondence between aprocess and a physical device can be easily visualized.

In the above example, the correspondence is represented by the colorcoding. However, the embodiment is not limited to this. For example,correspondence may be represented by a halftone pattern that is appliedto an area and/or an icon (e.g., presence or absence of a halftonepattern is switched depending on correspondence). Alternatively oradditionally, correspondence may be represented by a shape of an icon.

[Procedure of Executing a Workflow]

FIG. 18 is a sequence diagram showing an example of a procedure of theinformation processing system 500 to execute a workflow. FIGS. 19A and19B are examples of a screen for selecting a workflow.

S1: When a user operates the MFP 201, the MFP 201 displays a list ofworkflows. FIG. 19A shows an example of a workflow selection screen onwhich the list of workflows is displayed. The user selects a desiredworkflow from the workflows 1 to 3, and presses the OK button. Bypressing the OK button, execution of the workflow is started. Here,depending on necessity, a user may press a detail button to displayprocesses included in the workflow and an order of the processes.

When the execution of the workflow is started, the MFP 201 requests theuser to input a user name and a password, as shown in FIG. 19B. Here,the user name and the password are authentication information forexecuting the workflow. A user name and a password that are used forlogging in the MFP 201 may be used as the authentication information. Auser name and a password may preferably be included in a process flowdefinition. When a user name and a password are included in a processflow definition, authentication can be performed for physical devices.Consequently, security of the workflow can be enhanced.

S2: The user selects a workflow, and inputs a command for startingexecution of the workflow to the MFP 201.

S3: The MFP 201 starts execution of the workflow. For example, the MFP201 identifies a process and/or a machine ID described in the processflow definition.

S4: The MFP 201 transmits a workflow connection request to theidentified workflow processing server 100. This communication is forconfirming whether a physical device that is to execute the workflow isavailable for executing the workflow.

S5: The workflow processing server 100 executes a reception process forreceiving the workflow. The reception process for receiving the workflowis, for example, a process for attaching a unique JobID to the workflow.

S6: The workflow processing server 100 starts processing of theworkflow. Here, to start processing of the workflow means that theworkflow is executed when a process flow definition is received.

S7: The workflow processing server 100 transmits workflow receptioninformation (e.g., the JobID) to the MFP 201.

S8: When the MFP 201 confirms that the workflow can be executed, the MFP201 starts executing the processes 1 to 5. The job receiver 33 parsesthe process flow definition. This parsing process is for confirming thatthe MFP 201 is to execute processing of the current point.

S9: When the MFP 201 determines, as a result of the parsing process,that the MFP 102 is to execute processing, the flow control unit 22executes processing that is assigned to the MFP 201 by using the plug-in21. The process 1 is an input process. Accordingly, job data isprepared, for example, by scanning an original document, or by readingout or receiving e-mail data that is specified as job data.

S10: The flow control unit 22 updates the process flow definition byupdating the current point with the subsequent process. The job data andthe process flow definition are stored in the job queue 35.

Steps S8 to S10 are repeated for each of the processes. When the processflow definition is updated after the processes 1 and 2 are executed, thecurrent point is updated to be the connection process of the process2-1. The job receiver 33 parses the process flow definition, anddetermines that the process is the connection process (S8). Accordingly,the flow control unit 22 requests the job transmitter 32 to transmitsthe job without executing the process (S9). Then, the flow control unit22 updates the process flow definition (S10).

S11: As the connection process, the job transmitter 32 transmits theprocess flow definition and the job data to the workflow processingserver 100, while associating the JobID with the process flow definitionand the job data. During steps S11 to S15, the MFP 201 may query theworkflow processing server for progress of the processing.

S12: The procedure of the workflow processing server 100 is the same asthat of the MFP 201. The job receiver 33 stores the process flowdefinition and the job data in the job queue 35, and parses the processflow definition.

S13: When the job receiver 33 determines, as a result of the parsingprocess, that the process is to be executed by the workflow processingserver 100, the flow control unit 22 executes the process that isassigned to the workflow processing server 100 by using the plug-in 21.

S14: The flow control unit 22 updates the process flow definition byupdating the current point with the subsequent process.

When the process flow definition is updated, the current point isupdated to be the connection process of the process 3-1 (S12).Accordingly, the flow control unit 22 requests the job transmitter 32 totransmit the job without executing the process (S13). The flow controlunit 22 updates the process flow definition (S14).

S15: As the connection process, the job transmitter 32 transmits theprocess flow definition and the job data to the MFP 201.

S16: The job receiver 33 stores the process flow definition and the jobdata in the job queue 35, and the job receiver 33 parses the processflow definition.

S17: When the job receiver 33 determines, as a result of the parsingprocess, that the process is to be executed by the MFP 201, the flowcontrol unit 22 executes the process that is assigned to the MFP 201 byusing the plug-in 21.

S18: The flow control unit 22 updates the process flow definition byupdating the current point with the subsequent process. Steps S16 to S18are repeated for the processes 4 and 5.

As described above, the information processing system 500 according tothis embodiment displays the logical flow field and the physical deviceflow field in a single screen. Accordingly, an administrator can easilydefine a process flow definition. Additionally, correspondence betweenan upstream process and a physical device can be applied to an insertedprocess. Thus, operational steps for an administrator can be reduced. Bysetting a plurality of methods of modifying correspondence in advance, adesired method of modifying the correspondence can be selected. Forexample, only correspondence between a part of processes and a physicaldevice can be modified. Alternatively, correspondence between alldownstream processes and a physical device can be modified.

In the above-described example, a location of a physical device thatexecutes a workflow is not particularly limited. A workflow may includea process that is to be executed by a cloud computer (which is referredto as “cloud,” hereinafter) on the Internet.

FIG. 20 is a diagram showing a schematic configuration of theinformation processing system 500 according to another example. Theworkflow execution/request device 200 and the workflow processing server100 are located within an office. The cloud 600 is located outside theoffice. Accordingly, in order for the cloud 600 to communicate with theworkflow processing server 100 and/or the workflow execution/requestdevice 200, communication is to be performed across a firewall 601.

However, the firewall 601 may prevent the cloud 600 to access the systeminside the office. Accordingly, it may be difficult to return theworkflow executed by the cloud 600 to the system inside the office.Hereinafter, an example of the information processing system 500 isexplained that may conform to cloud computing.

FIG. 21A is a diagram illustrating an example of an outline of executionof a workflow by the information processing system 500. Suppose that theprocesses 1 and 2 are to be executed by the MFP 201, the process 3 is tobe executed by the cloud 600, and the processes 4 and 5 are to beexecuted by the MFP 201. In this case, the workflow execution/requestdevice 200 (i.e., MFP 201) that executes the process 2 polls the cloud600. Here, polling is to query the cloud 600 for completion of theprocessing. When the cloud 600 responds to the query from the systeminside the office, the cloud 600 can transmits the process flowdefinition and the job data to the system inside the office. In general,for a firewall, a setting can be made such that transmission of aresponse is allowed that is from a destination IP address of a packettransmitted from the system inside the office by an administrator or thelike (i.e., for a case where an IP address of an external transmissionsource of communication corresponds to an IP address of a destinationthat is set for communication from the system inside the office).Accordingly, when such a setting is made for the firewall 601, theprocess flow definition and the job data can be received as a responseto a packet that is transmitted from a physical device inside theoffice.

FIG. 21B is a diagram illustrating examples of the workflow including aprocess to be executed by the workflow processing server 100, and theinformation processing system 500 that executes the workflow. Supposethat the process 1 is to be executed by the MFP 201, the process 2 is tobe executed by the workflow processing server 100, the process 3 is tobe executed by the cloud 600, the process 4 is to be executed by theworkflow processing server 100, and the process 5 is to be executed bythe MFP 201. In this case, the workflow processing server that executesthe process 2 polls the cloud 600.

In the above example, the physical device that executes the processimmediately prior to the process to be executed by the cloud 600 pollsthe cloud 600. However, the embodiment is not limited to this. Forexample, the physical device that is to execute the process immediatelyafter the process to be executed by the cloud 600 may poll the cloud600. Alternatively, the workflow execution/request device 200 may alwayspoll the cloud 600. In the example described below, it is assumed thatthe physical device that executes the process immediately prior to theprocess to be executed by the cloud 600 polls the cloud 600.

[Process Flow Definition Including a Polling Process]

A process flow definition may include a polling process, so that aphysical device inside the office can poll the cloud 600. As explainedabove, an administrator creates a process flow definition such as shownin FIG. 8A. The process flow definition creating unit 43 of theadministration server 250 creates a process flow definition including aconnection process. In this example, the process flow definitioncreating unit 43 creates a process flow definition including a pollingprocess.

FIGS. 22A and 22B are diagrams illustrating examples of a process flowdefinition for polling. The process flow definition creating unit 43identifies, by referring to the process flow definition into which theconnection processes of FIG. 22A are inserted, a physical device (thecloud 600) that is defined as the physical device after the connectionprocess. As shown in FIG. 22A, the process 3 is to be executed by thecloud 600. The device list table 45 registers that the physical deviceto execute the process is the cloud 600, for example.

As shown in FIG. 22B, the process flow definition creating unit 43creates another process flow definition for polling such that theprocess 3 is defined to be a polling process, and the physical devicefor executing the process 3 is defined to be the MFP 201 that is toexecute the process 2-1. It suffices if a polling process can beexecuted by this process flow definition for polling. The processes 1 to2-1 are defined to be blank (i.e., the processes 1 to 2-1 are not to beexecuted). The cloud 600 that executes the process 3 is the only onetarget of polling. The IP address and the like of the cloud 600 may beregistered in the device list table 45.

For a workflow with which a process flow definition and job data are tobe received from the cloud 600 more than once, process flow definitionsfor polling may be created such that the number of the created processflow definitions for polling is equal to the number of times that theprocess flow definition and the job data are to be received from thecould 600.

During execution of the workflow, the physical device updates theprocess flow definition depending on progress of the processing, and thephysical device updates the current point of the process flow definitionfor polling. When the process of the process flow definition is updatedto be the process 3, and when the current point of the process flowdefinition for polling is updated to be the process 3, only the processflow definition and the job data are transmitted to the cloud 600. Inthe process flow definition for polling, the physical device that is toexecute the process 3 is defined to be the MFP 201. Accordingly, theprocess flow definition for polling is held by the MFP 201. In thismanner, the MFP 201 can poll the cloud 600. In the process flowdefinition for polling, there is no process after the process 3.Accordingly, after the polling process is completed, the process flowdefinition for polling is discarded.

A physical device may create the process flow definition for pollingduring execution of a workflow. When the current point is a connectionprocess, and when a process after the connection process is to beexecuted by a cloud, the physical device may create the process flowdefinition for polling. In this case, the physical device that createdthe process flow definition for polling is to execute the pollingprocess. Accordingly, the physical device executes the polling process.

FIG. 23 is a flowchart showing another example of the procedure of theadministrator's PC 150 and the administration server 250 for creatingthe process flow definition. The flow chart of FIG. 23 is almost thesame as that of FIG. 11. However, as shown in the flowchart of FIG. 23,after the process flow definition creating unit 43 inserts a connectionprocess (S240) immediately prior to switching of a physical device, adetermination is made as to whether a physical device that is to executethe process after the connection process is a cloud or not (S245).

When the physical device that is to execute the process after theconnection process is a cloud (S245: Yes), the process flow definitioncreating unit 43 creates a process flow definition for polling (S246).The process after step S246 is the same as that of FIG. 11. FIG. 24 is asequence diagram showing another example of the procedure of theinformation processing system 500 for executing the workflow. Theprocedure of FIG. 24 is almost the same as that of FIG. 18. Theprocedure of FIG. 24 is different from that of FIG. 18 in the procedureof executing the process 3.

By steps S8 to S10, the current point of the process flow definition isupdated to be the process 3, and the current point of the process flowdefinition for monitoring is updated to be the process 3.

S11: As the connection process, the job transmitter 32 transmits theprocess flow definition and the job data to the cloud 600. The procedureof the cloud 600 is the same as that of FIG. 18.

S31: The job receiver 33 parses the process flow definition. Here, thejob queue 35 stores at least the process flow definition for polling.

S32: The job receiver 33 determines, as a result of the parsing process,that the MFP 201 is to execute the polling process. Accordingly, the jobcontroller 23 of the MFP 201 (or the flow control unit 22 of the MFP201) executes the polling process for polling the cloud 600. The jobcontroller 23 attempts to update the process flow definition for pollingby updating the current point with the subsequent process. However, thejob controller 23 discards the process flow definition for pollingbecause there is not subsequent process.

S15: As the connection process, a job transmitter 32 of the cloud 600transmits the process flow definition and the job data to the MFP 201 asa response to a query from the MFP 201.

The process after step S15 is the same as that of FIG. 18.

As explained above, the information processing system 500 according tothis embodiment displays the logical flow field and the physical deviceflow field in a single screen. Accordingly, an administrator can easilydefine a process flow definition. Additionally, with the informationprocessing system 500, a workflow can be easily and flexibly definedsuch that processing is executed across a firewall.

Hereinabove, a process flow definition creating system, a process flowdefinition creating device, and a method of creating a process flowdefinition are explained by the embodiment. However, the presentinvention is not limited to the specifically disclosed embodiment, andvariations and modifications may be made within the scope of the presentinvention. Specific examples of numerical values are used in order tofacilitate understanding of the invention. However, these numericalvalues are simply illustrative, and any other appropriate values may beused, except as indicated otherwise. The separations of the sections ofthe specification are not essential to the present invention. Dependingon necessity, subject matter described in two or more sections may becombined and used, and subject matter described in a section may beapplied to subject matter described in another section (provided thatthey do not contradict). A boundary of a functional unit or a processingunit in a functional block may not correspond to a boundary of aphysical component. An operation by a plurality of functional units maybe physically executed by a single component. Alternatively, anoperation by a single functional unit may be physically executed by aplurality of components.

The present invention can be implemented in any convenient form, forexample using dedicated hardware, or a mixture of dedicated hardware andsoftware. The present invention may be implemented as computer softwareimplemented by one or more network processing apparatuses. The networkcan comprise any conventional terrestrial or wireless communicationsnetwork, such as the Internet. The processing apparatuses can compromiseany suitable programmed apparatuses such as a general purpose computer,personal digital assistant, mobile telephone (such as a WAP or3G-compliant phone) and so on. Since the present invention can beimplemented as software, each and every aspect of the present inventionthus encompasses computer software implementable on a programmabledevice. The computer software can be provided to the programmable deviceusing any storage medium for storing processor readable code such as afloppy disk, hard disk, CD ROM, magnetic tape device or solid statememory device. The hardware platform includes any desired hardwareresources including, for example, a central processing unit (CPU), arandom access memory (RAM), and a hard disk drive (HDD). The CPU mayinclude processors of any desired kinds and numbers. The RAM may includeany desired volatile or nonvolatile memories. The HDD may include anydesired nonvolatile memories capable of recording a large amount ofdata. The hardware resources may further include an input device, anoutput device, and a network device in accordance with the type of theapparatus. The HDD may be provided external to the apparatus as long asthe HDD is accessible from the apparatus. In this case, the CPU, forexample, the cache memory of the CPU, and the RAM may operate as aphysical memory or a primary memory of the apparatus, while the HDD mayoperate as a secondary memory of the apparatus.

The present application is based on and claims the benefit of priorityof Japanese priority application No. 2013-054326 filed on Mar. 15, 2013,the entire contents of which are hereby incorporated herein byreference.

What is claimed is:
 1. A process flow definition creating systemconfigured to provide a process flow definition to a system forexecuting processes in an order in accordance with the process flowdefinition for defining the processes to be executed by correspondingdevices and the order of executing the processes, the process flowdefinition creating system comprising: a device list storage unitconfigured store a list of the devices; a screen information storageunit configured to store screen information, wherein the screeninformation is for displaying a first field and a second field, thefirst field is for setting the processes in the order, and the secondfield is for setting the devices that are to execute the correspondingprocesses; a display control unit configured to parse the screeninformation, and configured to display the parsed screen information; asetting reception unit configured to receive a setting for the firstfield and a setting for the second field, wherein the setting for thefirst field defines the processes and the order of the processes, andthe setting for the second field defines correspondence between theprocesses and the devices that are to execute the processes; adefinition creating unit configured to create the process flowdefinition, based on the order of the processes and the devicescorresponding to the processes that are received by the settingreception unit; and a definition storage unit configured to store theprocess flow definition.
 2. The process flow definition creating systemaccording to claim 1, wherein the display control unit is configured todisplay the processes in the first field while visually associating theprocesses in the first field with the devices in the second field. 3.The process flow definition creating system according to claim 2wherein, when the setting reception unit receives an addition of aprocess to the first field in a state in which the processes in thefirst field are visually associated with the devices in the secondfield, the display control unit displays the added process whilevisually associating the added process with the device that isassociated with the last process in the order.
 4. The process flowdefinition creating system according to claim 2, wherein, when thesetting reception unit receives an addition of a device to the secondfield and new correspondence between the added device and the processthat is associated with the device other than the added device in thestate in which the processes in the first field are visually associatedwith the devices in the second field, the display control unit isconfigured to display the process associated with the added device bythe new correspondence and the downstream processes that are downstreamthe process associated with the added device while visually associatingthe process associated with the added device and the downstreamprocesses with the added device.
 5. The process flow definition creatingsystem according to claim 2, wherein, when the setting reception unitreceives an addition of a device to the second field and newcorrespondence between the added device and the process that isassociated with the device other than the added device in the state inwhich the processes in the first field are visually associated with thedevices in the second field, the display control unit is configured todisplay the process that is associated with the added device by the newcorrespondence while visually associating only the process that isassociated with the added device with the added device, and the displaycontrol unit is configured to display the downstream processes that aredownstream the process that is associated with the added device whilevisually associating the downstream processes with the device that isadded downstream the added device.
 6. The process flow definitioncreating system according to claim 2, wherein, when the settingreception unit receives an addition of a device to the second field andnew correspondence between the added device and the process that isassociated with the device other than the added device in the state inwhich the processes in the first field are visually associated with thedevices in the second field, the display control unit is configured todisplay a setting screen for receiving a setting of visually associatingthe added device with the downstream processes that are downstream theprocess that is associated with the added device by the newcorrespondence, a setting of visually associating only the process thatis associated with the added device with the added device, or a settingof visually associating the device that is added downstream the addeddevice with the downstream processes that are downstream the processthat is associated with the added device.
 7. The process flow definitioncreating system according to claim 2, wherein the display control unitis configured to display one of the devices and one or more processes ofthe processes with a first color, wherein the one or more processes areassociated with the one of the devices, and wherein the display controlunit is configured to display another one of the devices and another oneor more processes of the processes with a second color, wherein theother one or more processes are associated with the other one of thedevices, and the second color is different from the first color.
 8. Theprocess flow definition creating system according to claim 1, furthercomprising: a connection information storage unit configured to storeconnection information for communicating with the devices, wherein, whenone of the devices is to be switched to another one of the devices forexecuting one of the processes, the definition creating unit isconfigured to read out the connection information for the one of thedevices to transmit the process flow definition to the other one of thedevices from the connection information storage unit, and the definitioncreating unit is configured to insert the connection information as aconnection process immediately prior to the one of the process for whichthe one of the devices is to be switched.
 9. The process flow definitioncreating system according to claim 8, wherein, when one of the devicesis to be switched to another device for executing one of the processes,and when the other device is outside a firewall, the definition creatingunit is configured to create the process flow definition including apolling process such that one of the devices inside the firewallperiodically queries the other device for completion of the one of theprocesses.
 10. A process flow definition creating device comprising: adevice list storage unit configured store a list of devices; a screeninformation storage unit configured to store screen information, whereinthe screen information is for displaying a first field and a secondfield, the first field is for setting processes in an order, and thesecond field is for setting the devices that are to execute thecorresponding processes; a display control unit configured to parse thescreen information, and configured to display the parsed screeninformation; a setting reception unit configured to receive a settingfor the first field and a setting for the second field, wherein thesetting for the first field defines the processes and the order of theprocesses, and the setting for the second field defines correspondencebetween the processes and the devices that are to execute the processes;a definition creating unit configured to create a process flowdefinition, based on the order of the processes and the devicescorresponding to the processes that are received by the settingreception unit; a definition storage unit configured to store theprocess flow definition; and a network communication unit configured totransmit the process flow definition to a system for executing theprocesses in the order in accordance with the process flow definition.11. The process flow definition creating device according to claim 10,wherein the display control unit is configured to display the processesin the first field while visually associating the processes in the firstfield with the devices in the second field.
 12. The process flowdefinition creating device according to claim 11 wherein, when thesetting reception unit receives an addition of a process to the firstfield in a state in which the processes in the first field are visuallyassociated with the devices in the second field, the display controlunit displays the added process while visually associating the addedprocess with the device that is associated with the last process in theorder.
 13. The process flow definition creating device according toclaim 11, wherein, when the setting reception unit receives an additionof a device to the second field and new correspondence between the addeddevice and the process that is associated with the device other than theadded device in the state in which the processes in the first field arevisually associated with the devices in the second field, the displaycontrol unit is configured to display the process associated with theadded device by the new correspondence and the downstream processes thatare downstream the process associated with the added device whilevisually associating the process associated with the added device andthe downstream processes with the added device.
 14. The process flowdefinition creating device according to claim 11, wherein, when thesetting reception unit receives an addition of a device to the secondfield and new correspondence between the added device and the processthat is associated with the device other than the added device in thestate in which the processes in the first field are visually associatedwith the devices in the second field, the display control unit isconfigured to display the process that is associated with the addeddevice by the new correspondence while visually associating only theprocess that is associated with the added device with the added device,and the display control unit is configured to display the downstreamprocesses that are downstream the process that is associated with theadded device while visually associating the downstream processes withthe device that is added downstream the added device.
 15. The processflow definition creating device according to claim 11, wherein, when thesetting reception unit receives an addition of a device to the secondfield and new correspondence between the added device and the processthat is associated with the device other than the added device in thestate in which the processes in the first field are visually associatedwith the devices in the second field, the display control unit isconfigured to display a setting screen for receiving a setting ofvisually associating the added device with the downstream processes thatare downstream the process that is associated with the added device bythe new correspondence, a setting of visually associating only theprocess that is associated with the added device with the added device,or a setting of visually associating the device that is added downstreamthe added device with the downstream processes that are downstream theprocess that is associated with the added device.
 16. The process flowdefinition creating device according to claim 11, wherein the displaycontrol unit is configured to display one of the devices and one or moreprocesses of the processes with a first color, wherein the one or moreprocesses are associated with the one of the devices, and wherein thedisplay control unit is configured to display another one of the devicesand another one or more processes of the processes with a second color,wherein the other one or more processes are associated with the otherone of the devices, and the second color is different from the firstcolor.
 17. The process flow definition creating device according toclaim 10, further comprising: a connection information storage unitconfigured to store connection information for communicating with thedevices, wherein, when one of the devices is to be switched to anotherone of the devices for executing one of the processes, the definitioncreating unit is configured to read out the connection information forthe one of the devices to transmit the process flow definition to theother one of the devices from the connection information storage unit,and the definition creating unit is configured to insert the connectioninformation as a connection process immediately prior to the one of theprocess for which the one of the devices is to be switched.
 18. Theprocess flow definition creating device according to claim 17, wherein,when one of the devices is to be switched to another device forexecuting one of the processes, and when the other device is outside afirewall, the definition creating unit is configured to create theprocess flow definition including a polling process such that one of thedevices inside the firewall periodically queries the other device forcompletion of the one of the processes.
 19. A method of creating aprocess flow definition, wherein the process flow definition is to beprovided to a system for executing processes in an order in accordancewith the process flow definition, and the process flow definitiondefines the processes to be executed by corresponding devices and theorder of executing the processes, the method comprising: storing a listof the devices; storing screen information, wherein the screeninformation is for displaying a first field and a second field, thefirst field is for setting the processes in the order, and the secondfield is for setting the devices that are to execute the correspondingprocesses; parsing the screen information, and displaying the parsedscreen information; receiving a setting for the first field and asetting for the second field, wherein the setting for the first fielddefines the processes and the order of the processes, and the settingfor the second field defines correspondence between the processes andthe devices that are to execute the processes; creating the process flowdefinition, based on the order of the processes and the devicescorresponding to the processes that are received by the receiving; andstoring the process flow definition.